bug: Fix OAuth flow, session/token handling, and frontend OAuth navigation (Google & GitHub) #55
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
04shubham7
added
bug
|
Resolve merge conflicts |
|
Resolve Conflicts Pls |
|
Done 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
fixing full Google and GitHub OAuth authentication by ensuring backend callbacks weren’t intercepted by client-side routing.
Set up Passport strategies to issue rotated access and refresh tokens, manage secure httpOnly refresh cookies, and fix session creation in the database.
Updated the frontend flow to automatically exchange refresh cookies for new access tokens and logout behavior.
Semver Changes
Issues
#52
Checklist